<xs:documentation>Either a fully-qualified path name or a registry value that points to the location in which your Help files should be installed. To copy your files to the BDS "ThirdParty" folder, use "bdsdocs" as your InstallDest and prepend each file name in your file list with the path "\Help\ThirdParty\" (only).</xs:documentation>
<xs:documentation>4 digit number indicating the language of the source files. Only required if internationalizing.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Versioning" minOccurs="0">
<xs:annotation>
<xs:documentation>Used only when you want to install a new file set over an old set. Recognized values: "none" (default) means replace installed files with update files of the same names, regardless of version numbers or date/time stamps; "date" copies only newer files; "file" instructs the script to compare file versions on the old and new files, and replace only those that show older version numbers. Another recognized option--used by the Borland documentation set-- is "extended." This value instructs the script to parse a four-segment numeric version stamp (delimited by periods), with the first two segments representing a file's major and minor version numbers, the third segment representing a StockKeeping Unit (SKU; e.g., Enterprise, Professional, Personal editions of a product), and the final segment representing a localized build (LCID number). A typical "extended" version number might be "1.1034.2.1031", which, in your scheme, might mean version 1, build 1034, the second of three SKUs, and a German file set. When file updates are compared to installed files, users are warned if the SKU or LCID numbers do not match. If the user decides to proceed anyway, all installed files are replaced with files of the same names from the update set. If the SKUs and LCID numbers match (and the question is not posed), then the file version numbers (first two segments of the string) are compared, and all files with older version numbers are replaced. If this key is absent or values other than those shown here are used, version comparisons are not performed.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="none"/>
<xs:enumeration value="date"/>
<xs:enumeration value="file"/>
<xs:enumeration value="extended"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="InstallSrc" type="xs:string">
<xs:annotation>
<xs:documentation>Specifies the location of your Help files on your installation media or local folder, relative to the location of the regHelp.js script. An asterisk (*) appended to the path means your files are all in the same source folder. If the asterisk is not present, the script adds any path specs from the file list to the InstallSrc path spec when attempting to install files.</xs:documentation>
<xs:documentation>Root directory for .NET Framework installation.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="ShortCut" minOccurs="0">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=".+\.[Ll][Nn][Kk]"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:choice>
<xs:element name="Merge">
<xs:annotation>
<xs:documentation>Contains information needed to merge a set of documentation files with the existing Borland TOC and documentation set.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="TOCTitle" minOccurs="0">
<xs:annotation>
<xs:documentation>Your table of contents heading, used in a rewrite of the parent BDS Table of Contents (bds.HxT) file. If you don't want your table of contents merged with bds.HxT, you can leave this line (and MergeTOCurl) out. Note: If refreshing or reregistering an installed file set, the script checks for this value in the existing bds.HxT. If it finds it, it skips the .HxT rewrite. Thus, if adding new files to an existing installation, or if you change contents information, you should first unregister (to remove existing contents information), then reregister your file set to update the contents with your new information.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="TOCUrl" minOccurs="0">
<xs:annotation>
<xs:documentation>Used only if a MergeTOCtitle is specified. If merging your table of contents, this fully-qualified URL points to an introductory topic contained in one of your Help files. The URL must match the URL you would see in the Address field of the Document Explorer Help viewer when viewing your introductory topic, with the namespace portion replaced by "borland.bds".</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FileList">
<xs:annotation>
<xs:documentation>A list of all Help 2.0 files that may be installed, refreshed, or reregistered at any point. If you prepend file names with a path spec, the script appends your file path spec to the InstallDest path, creating a list of installation locations. If you do not have compiled index (HXI) files in your set, the script will register only the HXS files, and your topics will not be merged into the BDS index. Note: InstallDest\file list paths and names may also be used to remove files from their installed locations.</xs:documentation>
<xs:documentation>A table of contents file (*.Hxt) for the associated help topics.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=".+\.[Hh][Xx][Tt]"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="Filters" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Plugin">
<xs:annotation>
<xs:documentation>Contains information needed to plug a set of documentation files with the existing Borland documentation set.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="Description">
<xs:annotation>
<xs:documentation>Description for the namespace.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Namespace">
<xs:annotation>
<xs:documentation>The namespace the helpfiles will be included in.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FileList">
<xs:annotation>
<xs:documentation>A list of all Help 2.0 files that may be installed, refreshed, or reregistered at any point. If you prepend file names with a path spec, the script appends your file path spec to the InstallDest path, creating a list of installation locations. If you do not have compiled index (HXI) files in your set, the script will register only the HXS files, and your topics will not be merged into the BDS index. Note: InstallDest\file list paths and names may also be used to remove files from their installed locations.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="Attributes">
<xs:annotation>
<xs:documentation>A attributes file (*.Hxa) for the associated help topics.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=".+\.[Hh][Xx][Aa]"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Collection">
<xs:annotation>
<xs:documentation>A collection file (*.Hxc) for the associated help topics.</xs:documentation>
<xs:documentation>A table of contents file (*.Hxt) for the associated help topics.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=".+\.[Hh][Xx][Tt]"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="Filters" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Standalone">
<xs:annotation>
<xs:documentation>Contains information needed to create a new stand-alone help system.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="Description">
<xs:annotation>
<xs:documentation>Description for the namespace.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Namespace">
<xs:annotation>
<xs:documentation>The namespace the helpfiles will be included in.</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="FileList">
<xs:annotation>
<xs:documentation>A list of all Help 2.0 files that may be installed, refreshed, or reregistered at any point. If you prepend file names with a path spec, the script appends your file path spec to the InstallDest path, creating a list of installation locations. For stand-alone help systems, you must include both HxI and HxS files. Note: InstallDest\file list paths and names may also be used to remove files from their installed locations.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="Attributes">
<xs:annotation>
<xs:documentation>A attributes file (*.Hxa) for the associated help topics.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=".+\.[Hh][Xx][Aa]"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="Collection">
<xs:annotation>
<xs:documentation>A collection file (*.Hxc) for the associated help topics.</xs:documentation>
<xs:documentation>A table of contents file (*.Hxt) for the associated help topics.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=".+\.[Hh][Xx][Tt]"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="Filters" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Filters">
<xs:annotation>
<xs:documentation>A list of one or more filters. </xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="Filter" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>A filter for the help system. The specification portion must be in accordance with Help 2.0 authoring conventions. Validation is not performed by the regHelp script, so if the filter is badly formed, it will generate an error message when selected in the reindexed Help system.</xs:documentation>
